Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update react monorepo to v18 (major) #252

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 21, 2022

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
react (source) ^16.9.0 || ^17.0.0 -> ^16.9.0 || ^17.0.0 || ^18.0.0 age adoption passing confidence
react (source) 17.0.2 -> 18.3.1 age adoption passing confidence
react-dom (source) ^16.9.0 || ^17.0.0 -> ^16.9.0 || ^17.0.0 || ^18.0.0 age adoption passing confidence
react-dom (source) 17.0.2 -> 18.3.1 age adoption passing confidence
react-test-renderer (source) 17.0.2 -> 18.3.1 age adoption passing confidence

Release Notes

facebook/react (react)

v18.3.1

Compare Source

v18.3.0

Compare Source

v18.2.0

Compare Source

React DOM
React DOM Server
Server Components (Experimental)

v18.1.0

Compare Source

React DOM
React DOM Server
ESLint Plugin: React Hooks
Use Subscription

v18.0.0

Compare Source

Below is a list of all new features, APIs, deprecations, and breaking changes.
Read React 18 release post and React 18 upgrade guide for more information.

New Features
React
  • useId is a new hook for generating unique IDs on both the client and server, while avoiding hydration mismatches. It is primarily useful for component libraries integrating with accessibility APIs that require unique IDs. This solves an issue that already exists in React 17 and below, but it’s even more important in React 18 because of how the new streaming server renderer delivers HTML out-of-order.
  • startTransition and useTransition let you mark some state updates as not urgent. Other state updates are considered urgent by default. React will allow urgent state updates (for example, updating a text input) to interrupt non-urgent state updates (for example, rendering a list of search results).
  • useDeferredValue lets you defer re-rendering a non-urgent part of the tree. It is similar to debouncing, but has a few advantages compared to it. There is no fixed time delay, so React will attempt the deferred render right after the first render is reflected on the screen. The deferred render is interruptible and doesn't block user input.
  • useSyncExternalStore is a new hook that allows external stores to support concurrent reads by forcing updates to the store to be synchronous. It removes the need for useEffect when implementing subscriptions to external data sources, and is recommended for any library that integrates with state external to React.
  • useInsertionEffect is a new hook that allows CSS-in-JS libraries to address performance issues of injecting styles in render. Unless you’ve already built a CSS-in-JS library we don’t expect you to ever use this. This hook will run after the DOM is mutated, but before layout effects read the new layout. This solves an issue that already exists in React 17 and below, but is even more important in React 18 because React yields to the browser during concurrent rendering, giving it a chance to recalculate layout.
React DOM Client

These new APIs are now exported from react-dom/client:

  • createRoot: New method to create a root to render or unmount. Use it instead of ReactDOM.render. New features in React 18 don't work without it.
  • hydrateRoot: New method to hydrate a server rendered application. Use it instead of ReactDOM.hydrate in conjunction with the new React DOM Server APIs. New features in React 18 don't work without it.

Both createRoot and hydrateRoot accept a new option called onRecoverableError in case you want to be notified when React recovers from errors during rendering or hydration for logging. By default, React will use reportError, or console.error in the older browsers.

React DOM Server

These new APIs are now exported from react-dom/server and have full support for streaming Suspense on the server:

  • renderToPipeableStream: for streaming in Node environments.
  • renderToReadableStream: for modern edge runtime environments, such as Deno and Cloudflare workers.

The existing renderToString method keeps working but is discouraged.

facebook/react (react-dom)

v18.3.1

Compare Source

v18.3.0

Compare Source

v18.2.0

Compare Source

React DOM
React DOM Server
Server Components (Experimental)

v18.1.0

Compare Source

React DOM
React DOM Server
ESLint Plugin: React Hooks
Use Subscription

v18.0.0

Compare Source

Below is a list of all new features, APIs, deprecations, and breaking changes.
Read React 18 release post and React 18 upgrade guide for more information.

New Features
React
  • useId is a new hook for generating unique IDs on both the client and server, while avoiding hydration mismatches. It is primarily useful for component libraries integrating with accessibility APIs that require unique IDs. This solves an issue that already exists in React 17 and below, but it’s even more important in React 18 because of how the new streaming server renderer delivers HTML out-of-order.
  • startTransition and useTransition let you mark some state updates as not urgent. Other state updates are considered urgent by default. React will allow urgent state updates (for example, updating a text input) to interrupt non-urgent state updates (for example, rendering a list of search results).
  • useDeferredValue lets you defer re-rendering a non-urgent part of the tree. It is similar to debouncing, but has a few advantages compared to it. There is no fixed time delay, so React will attempt the deferred render right after the first render is reflected on the screen. The deferred render is interruptible and doesn't block user input.
  • useSyncExternalStore is a new hook that allows external stores to support concurrent reads by forcing updates to the store to be synchronous. It removes the need for useEffect when implementing subscriptions to external data sources, and is recommended for any library that integrates with state external to React.
  • useInsertionEffect is a new hook that allows CSS-in-JS libraries to address performance issues of injecting styles in render. Unless you’ve already built a CSS-in-JS library we don’t expect you to ever use this. This hook will run after the DOM is mutated, but before layout effects read the new layout. This solves an issue that already exists in React 17 and below, but is even more important in React 18 because React yields to the browser during concurrent rendering, giving it a chance to recalculate layout.
React DOM Client

These new APIs are now exported from react-dom/client:

  • createRoot: New method to create a root to render or unmount. Use it instead of ReactDOM.render. New features in React 18 don't work without it.
  • hydrateRoot: New method to hydrate a server rendered application. Use it instead of ReactDOM.hydrate in conjunction with the new React DOM Server APIs. New features in React 18 don't work without it.

Both createRoot and hydrateRoot accept a new option called onRecoverableError in case you want to be notified when React recovers from errors during rendering or hydration for logging. By default, React will use reportError, or console.error in the older browsers.

React DOM Server

These new APIs are now exported from react-dom/server and have full support for streaming Suspense on the server:

  • renderToPipeableStream: for streaming in Node environments.
  • renderToReadableStream: for modern edge runtime environments, such as Deno and Cloudflare workers.

The existing renderToString method keeps working but is discouraged.

facebook/react (react-test-renderer)

v18.3.1

Compare Source

v18.3.0

Compare Source

v18.2.0

Compare Source

React DOM
React DOM Server
Server Components (Experimental)

v18.1.0

Compare Source

React DOM
React DOM Server
ESLint Plugin: React Hooks
Use Subscription

v18.0.0

Compare Source

Below is a list of all new features, APIs, deprecations, and breaking changes.
Read React 18 release post and React 18 upgrade guide for more information.

New Features
React
  • useId is a new hook for generating unique IDs on both the client and server, while avoiding hydration mismatches. It is primarily useful for component libraries integrating with accessibility APIs that require unique IDs. This solves an issue that already exists in React 17 and below, but it’s even more important in React 18 because of how the new streaming server renderer delivers HTML out-of-order.
  • startTransition and useTransition let you mark some state updates as not urgent. Other state updates are considered urgent by default. React will allow urgent state updates (for example, updating a text input) to interrupt non-urgent state updates (for example, rendering a list of search results).
  • useDeferredValue lets you defer re-rendering a non-urgent part of the tree. It is similar to debouncing, but has a few advantages compared to it. There is no fixed time delay, so React will attempt the deferred render right after the first render is reflected on the screen. The deferred render is interruptible and doesn't block user input.
  • useSyncExternalStore is a new hook that allows external stores to support concurrent reads by forcing updates to the store to be synchronous. It removes the need for useEffect when implementing subscriptions to external data sources, and is recommended for any library that integrates with state external to React.
  • useInsertionEffect is a new hook that allows CSS-in-JS libraries to address performance issues of injecting styles in render. Unless you’ve already built a CSS-in-JS library we don’t expect you to ever use this. This hook will run after the DOM is mutated, but before layout effects read the new layout. This solves an issue that already exists in React 17 and below, but is even more important in React 18 because React yields to the browser during concurrent rendering, giving it a chance to recalculate layout.
React DOM Client

These new APIs are now exported from react-dom/client:

  • createRoot: New method to create a root to render or unmount. Use it instead of ReactDOM.render. New features in React 18 don't work without it.
  • hydrateRoot: New method to hydrate a server rendered application. Use it instead of ReactDOM.hydrate in conjunction with the new React DOM Server APIs. New features in React 18 don't work without it.

Both createRoot and hydrateRoot accept a new option called onRecoverableError in case you want to be notified when React recovers from errors during rendering or hydration for logging. By default, React will use reportError, or console.error in the older browsers.

React DOM Server

These new APIs are now exported from react-dom/server and have full support for streaming Suspense on the server:

  • renderToPipeableStream: for streaming in Node environments.
  • renderToReadableStream: for modern edge runtime environments, such as Deno and Cloudflare workers.

The existing renderToString method keeps working but is discouraged.


Configuration

📅 Schedule: Branch creation - "before 4am on Monday" in timezone America/New_York, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Contributor Author

renovate bot commented Nov 21, 2022

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @edx/[email protected]
npm error Found: [email protected]
npm error node_modules/react
npm error   dev react@"18.3.1" from the root project
npm error   peer react@">=16.3" from @fortawesome/[email protected]
npm error   node_modules/@fortawesome/react-fontawesome
npm error     @fortawesome/react-fontawesome@"0.2.0" from the root project
npm error   30 more (@fortawesome/react-fontawesome, @restart/context, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"^16.9.0 || ^17.0.0" from @edx/[email protected]
npm error node_modules/@edx/frontend-platform
npm error   dev @edx/frontend-platform@"8.0.1" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/react
npm error   peer react@"^16.9.0 || ^17.0.0" from @edx/[email protected]
npm error   node_modules/@edx/frontend-platform
npm error     dev @edx/frontend-platform@"8.0.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-05-06T10_52_12_350Z-eresolve-report.txt

npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-06T10_52_12_350Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 682a4f5 to a4c3b6b Compare November 28, 2022 08:34
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from a4c3b6b to a083ae7 Compare November 30, 2022 12:37
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from a083ae7 to 0012733 Compare December 8, 2022 12:22
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 0012733 to 6bbebba Compare December 22, 2022 01:07
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 6bbebba to 259d57e Compare January 9, 2023 10:19
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 3 times, most recently from 0ad00b7 to 5508cbc Compare January 20, 2023 07:31
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 4 times, most recently from fbe8de7 to fdeb6e9 Compare February 1, 2023 10:11
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from fdeb6e9 to 09aaca4 Compare February 13, 2023 13:45
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 09aaca4 to 5d793d2 Compare February 24, 2023 18:28
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 5d793d2 to 6ab11c3 Compare March 6, 2023 13:01
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 4 times, most recently from f861f18 to fccc6eb Compare March 20, 2023 11:43
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 6 times, most recently from ee5c11b to ae2aa7b Compare March 29, 2023 11:46
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 3 times, most recently from 46a67e1 to be813e0 Compare April 5, 2023 11:29
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 3 times, most recently from a6f520d to c1c4518 Compare July 22, 2024 12:39
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 3 times, most recently from 6d11c62 to 93ac5aa Compare August 5, 2024 09:38
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 3 times, most recently from 4f4658a to 3633982 Compare August 12, 2024 13:35
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from b43bfb7 to 87789d1 Compare August 19, 2024 12:06
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 3 times, most recently from 24def21 to 0c9854b Compare September 2, 2024 09:41
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 622e954 to 7ae422c Compare September 9, 2024 09:52
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 5 times, most recently from 5539937 to e5f5f4f Compare September 23, 2024 07:59
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 68fd648 to a84c90a Compare October 1, 2024 13:46
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from efb5048 to 994703c Compare October 14, 2024 07:40
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 994703c to b31300f Compare October 21, 2024 10:56
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 5c35ee6 to 28a7d14 Compare November 4, 2024 10:40
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 28a7d14 to 2418ba7 Compare November 11, 2024 11:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants